Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

Using default sample brokers

Most Unified Broker products have a default, sample broker that is immediately available for you to use. The purpose of these brokers is to help you quickly become familiar with and use the functionality associated with these products.

In most instances, the sample brokers require little, if any, modification and no validation. Although you can continue to use these sample brokers when you are operational in either a production or development mode, it is not advisable to do so. Consider modifying these files, using the edit capabilities of such tools as the Progress Explorer or mergeprop utility, for the purposes of security and tailoring them to your exact needs. See Chapter 10, "Configuration Basics," for details about these tools.

Note: A sample broker cannot be used connect to a database. If you elect to use a default, sample broker, you will need to modify it before attempting to perform a database connection.

Table 11–3 identifies each default, sample brokers associated with each Unified Broker product.

Table 11–3: Default sample broker for each Unified Broker product 

This Unified Broker product...	Has as its broker type. . .	And also supports the default broker identified as. . .
AppServer	AppServer Broker	asbroker1
OpenEdge Adapter for SonicMQ	Adapter for SonicMQ Broker	sonicMQ1
WebSpeed	WebSpeed Transaction Broker	wsbroker1
DataServer for MS SQL Server	DataServer MS SQL Broker	mssbroker1
ORACLE DataServer	ORACLE DataServer Broker	odbbroker1
DataServer for ODBC	DataServer for ODBC Broker	orabroker1
Name Server	NameServer Broker	NS1

Each Unified Broker process, default or user defined, manages only one Unified Broker process instance of the same type.

For more information on how to configure the Unified Broker process for a product, how clients specify connections, and how the Unified Broker manages connections with clients, see your product documentation.

Additional Unified Broker characteristics

The Unified Broker process:

Can register the following information with a controlling NameServer:
The broker’s location on the network.
The weight factor that you specify for load balancing.
The Application Service that you specify.
Note: Keep in mind that the NameServer is not required. Therefore, the registration of a Unified Broker with the NameServer is dependent on your specific implementation.

Manages connections between clients and the Unified Broker instance.
Provides other services unique to a Unified Broker product. For example, it maintains the status of each 4GL process running on an AppServer and scales the number of processes according to changing demand.

For more information on how to configure the Unified Broker process for a product, how clients specify connections, and how the Unified Broker manages connections with clients, see your product documentation.